That's one conclusion. I have another one.PS, with my first 6.0 firmware, I was also - for the first time - experiencing a lot of range gyration. Showing one number, driving a while, not depleting, going to sleep, waking up, showing a higher number, going to sleep, showing a real drop off. Before being concerned, I suggest see if it settles down after a week. I suspect they've made the algorithm far more sensitive to SOMETHING, so it bounces around until the averages take over.
As a software engineer I have an example handy from an applet I wrote eons ago ...
Suppose you're copying a file and you want to report the transfer rate. For the first, say, 60 blocks your transfer rate is jumping all over the place. As soon as you get some more data points the numbers start to stabilize until/unless you have some unusual events (like a disk drive goes bad or someone spikes the disk with some other higher priority activity).
I think the "gyration" is just another aspect of re-seeding the algorithm with data about the installed battery after having reset the historical data to, effectively, empty. This hypothesis doesn't require any "far more sensitive to SOMETHING" change to the algorithm.