2.1.0
Changes:
- Timers no longer start themselves - they must be started via timerInstance.start() or a observing a configured engagementEvent
- Timer start times now default to the time the timer was created; previously, a timestamp stored when the class loads would be used. To change the start time, set the startTime option
- Context-specific behavior fixes
- Better tests
- Updated build scripting