Fixed an issue that timers created by the TimedInterface wouldn't be registered with JMX because the timers were created lazily therefore at the time the composite monitor was registered with the monitor registry there wouldn't be any monitors to actually register with the mbean server. Now, all the timers are created when the object is first constructed. Fixed an issue that when CompositeMonitor methods were called the arguments were not being passed to the method which would cause an exception to occur when caling getValue(<value>). Added a test to verify inherited methods are timed as well.
Merge pull request #252 from ryanrupp/timedInterfaceFix

Fixed an issue that timers created by the TimedInterface wouldn't be reg...