I'm good with documentation that gives us a way to say "we told you so" when we end up being one bucket off and such. However, I still want to aim for principle of least surprise where possible. The original behaviors (rounding to nearest or truncating) clearly produced some surprising behaviors (seen if we scroll way way up in this thread) in some easy to hit cases. I think that the various prev stuff we've played with help reduce the surprising cases, but does not eliminate them. There will always be the potential for off-by-count-fp-edge things that turn into off-by-1000000x--in-reported-value behavior (the skip in count can move you across a wide swath of empty buckets), but these occurrences will be right at the noise point, in places that could've/would've happened with +/- one recorded value count too.