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

Should this be (currentTime > timestamp && currentTime - timestamp > threshold)

The current check expires any timestamp after the currentTimeMillis() in the iterator.  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.