Several checks currently log runtime problems to the
auditing system, e.g. RedundantThrows might generate
"Unable to get class information for InvalidMoveException."
These kind of messages should not go into the audit
report (which should only list the problems in the code
that has been inspected). Instead they should either be
reported to the log (e.g. appear in ant's build log) or
raise an exception and stop checkstyle - not sure which
approach is better, comments are welcome.