RangeError in Windows due to AtomicFixnum limit #125
Description
While looking into #124, I found that there's another Windows incompatibility. In events.rb, we're using a Concurrent::AtomicFixnum to store a millisecond timestamp value. AtomicFixnum has different maximum values depending on the system architecture, and on Windows that limit is too low for the values we're storing. This is a known issue with concurrent-ruby.