closes #164

Ran the test 10 times over and it was successful each time

instead of just an empty string. This should happen almost never, but
hopefully this will prompt people to report bugs if it does happen
instead of hiding them.

This is an enhancement and and a bug fix.  Models use polymorphic routes and should be considered safe as do arrays.  Treat arrays containing things other than models as unsafe as well.

There should never be the case where the target of a :call Sexp is a
symbol, it should always be either `nil` or a Sexp. Brakeman should not
be building invalid Sexps.

for the very few times the original Sexp `method_missing`
behavior is expected

Surprised this never caused any errors

Brakeman was generating invalid call Sexps with `:_hamlout`
as the target for `_hamlout.options` and `hamlout.buffer`.
However, these special Sexps were not really be handled in Brakeman
anywhere, and there was no real reason to make special Sexps for them.

If exceptions occured while formatting code,
OutputProcessor#format would return `nil`. Now it should return
a string instead so it can be used safely.

because it was checking the options for the wrong value

Basically, because the tracker caches the template names and the
rescanner was deleting the templates without clearing the cache. Should
use Tracker#reset_template instead

Fixes #120

Makes slightly more sense and doesn't seem to refer
to application path

Set ActiveSupport.escape_html_entities_in_json=true in versions >= 2.1.0 for autoescaping on a to_json call.