Instance for Double/Float is absolutely batty

Apparently, binary represents a Double as a tuple of (Integer, Int)? This means that doubles suffer a x3 or more size explosion, when really you could just record an IEEE floating point with the proper endian. This would also fix #64

Backwards compatibility might be a concern for fixing this, however.

Start by locating the Haskell Instance for Double/Float and read the discussion of issue #64. Check the current encoded representation and any existing tests before assessing the proposed IEEE floating-point representation. Done means the size expansion is addressed, #64 is covered, and the backwards-compatibility impact is tested or clearly resolved.

Written by the indexing model from the issue text.