It doesn't sound fishy at all, that was the most obvious explanation right off the bat. The battery was inconsistent when Safari was running, but consistent when Chrome was used in its place. That's a massive neon sign pointing to a bug in Safari causing problems, and loads of people said this as soon as the report came out.