Refactoring

> Originally at https://github.com/kevin-brown/mousetrap/pull/1

This is the pull request that will be used for code review, tracking progress, and eventually generating the patch set for this refactoring.
Short answer: after refactoring and cleaning, I noticed that this method doesn't use the state of an instance. That sounds like a static method to me. So I made it static. It's private because only code in the class uses it (for now).

Longer answer: if something naturally looks static (as described above) I prefer to make it so. Static methods are often prime candidates for reuse. And with less dependencies, they are in a better position to be refactored into a module function or another "library" class.

Deeper issues: if one finds many private static methods in a class, it could be a sign that we are not programming in an OO fashion. Hiding the issue by making all methods non-static would not change that fact, it would just make it harder to detect. In my mind, I didn't make it static, it was already static. I just labeled it as such.

Very deep issues: these are private :)