Changed to v2.0.1, which includes a significant API change for LatencyStats:

 - Eliminates forceIntervalSample() API call. getIntervalHistogram() (and the ...into and add... variants) now implicitly force an interval sample. This fits much better with the natural use cases, and is consistent with the way IntervalHistogramRecorder in HdrHistogram works.

 - Eliminates  accumulated histogram tracking. Callers can track accumulated histograms on their own if the wish to (by adding sampled interval histograms into them). Callers that don't perform and interval sampling during a run can basically use the interval histogram as an accumulated histogram for the whole run. With LatencyStats instances becoming more common, the extra overhead in space and work was not warranted.

 - The new API is not compatible with the previous one. But the lack of a forceIntervalSample() method will make that clear to any caller code. Changes to using the new API are very straightforward.
Merge remote-tracking branch 'origin/master'