Fixes #243 Tuples should no longer be squashed in the event store

> Seems like you are assuming that the times are synced perfectly between the server that wrote a mutation and the one this iterator is running on during scan/compaction. 

I'm not sure if that necessarily matters- for one, you'd assume they are being sync'd by NTP (i.e. the client code is somewhere in the cloud on either an edge node or an internal node. But 2, this isn't as much a problem for this particular filter as it is for the semantics of the Accumulo timestamp field- which come with their own caveats.