Alter some benchmarks to check:  Is it time to switch entirely to obj2?  Anecdatally, yes.
Alter some benchmarks to check:  Is it time to switch entirely to obj2?  Anecdatally, yes.

This is just with the CBOR benchmarks replaced at the moment (json rows copied here for context), but results are uniformly good-lookin':

old:

```
Benchmark_ArrayFlatIntToJson_Xlate-8             1000000              2075 ns/op
Benchmark_ArrayFlatIntToCbor_Xlate-8             1000000              1638 ns/op
Benchmark_ArrayFlatIntToJson_Stdlib-8            2000000               972 ns/op
Benchmark_ArrayFlatStrToJson_Xlate-8             1000000              2485 ns/op
Benchmark_ArrayFlatStrToCbor_Xlate-8             1000000              1940 ns/op
Benchmark_ArrayFlatStrToJson_Stdlib-8            1000000              1179 ns/op
```

new:

```
Benchmark_ArrayFlatIntToJson_Xlate-8              500000              2084 ns/op
Benchmark_ArrayFlatIntToCbor_Xlate-8             1000000              1339 ns/op
Benchmark_ArrayFlatIntToJson_Stdlib-8            2000000               989 ns/op
Benchmark_ArrayFlatStrToJson_Xlate-8             1000000              2447 ns/op
Benchmark_ArrayFlatStrToCbor_Xlate-8             1000000              1587 ns/op
Benchmark_ArrayFlatStrToJson_Stdlib-8            1000000              1081 ns/op
```

This new consistently-reflective code is, without any particularly interesting work re-optimizing it, doing a solid 20% better than the previous generation.  We're now solidly in line with comparable to stdlib.

Signed-off-by: Eric Myhre <2346ad27d7568ba9896f1b7da6b5991251debdf2@exultant.us>

polydawn/go-xlate,polydawn/go-xlate,polydawn/refmt,polydawn/refmt