Don't block NoMethodErrors from raising

This is bad practice, and I'm not quite sure why we do it.

In one case, it has a particularly annoying side-effect of not
being able to turn off the warnings, despite a NoMethodError being
expected.
Merge pull request #31 from shekibobo/raise-no-method-errors

Don't block NoMethodErrors from raising