insert new log entries chronologically, instead of assuming that the last entry to arrive is the latest. the previous assumption was invalid when the query was reset and historical log data was loaded from Chrome and Node.js simultaneously.
when merging events from Chrome and Node.js, and two timestamps are equal, sort by ticks. The tick numbers aren't comparable across processes, but this keeps the events from within a single process sorted properly relative to one another, which the unstable .sort() didn't do.
bump version to 0.2.11