An example of how mathn usage could be made explicit and optional

See my comment on issue #43 for information about this change.

The implicit inclusion of `mathn` breaks another gem we use. The bug is with mathn itself, but we find ourselves in a position where we need to use `ruby-units` and the other gem together.