the unit test uses compatible mode. The benchmarks measure compat,
default, and fastest.
This still fails for strings and slices and maps all over the place.
This fuzzes a type, marshals it with stdlib and json-iterator, compares,
then unmarshals with stdlib and json-iterator and compares. This is
checking for literal, byte-for-byte compatibility.
In every case the test is exactly the same.
It also include benchmark functions to compare stdlib vs json-iterator.
This depends on a couple PRs to be merged in gofuzz.