Perhaps i should have added some technical detail. Basically teh GWT long emulation uses a tuple of two numbers, the first holding the high 32 bits and the second the low 32 bits of the 64 bit long.
The library of course contains methods to add stuff like adding two "longs" and getting a "long" result. Within your GWT java code it just looks like two regular longs - one doesnt need to fiddle or be aware of the tuple. By using this approach GWt avoids the problem your probably alluding too, namely "longs" dropping the lower bits of precision which isnt acceptable in many cases.
Whilst floats are by definition imprecise / approximations of a value a whole number like a long isnt. GWT always holds a 64 bit long - maths using such longs never use precision. The exception to this is overflows but that accurately matches what occurs in Java etc when you add two very large long values which require more than 64 bits - eg 2^32-1 + 2^32-1.
To do the same for floating point numbers will require a similar approach. You will need to have a library that uses a tuple.