Property-based testing

I think, that the serializer is great subject for a [property-based tests](http://fsharpforfunandprofit.com/posts/property-based-testing/). As the serializer can actually generated and compile code in the runtime, the number of possible edge cases and tweak will be hard to catch.

Read the serializer implementation and the linked property-based testing article first. Define generated and compiled serialization cases that exercise edge cases and tweaks, then consider the work complete when the serializer has property-based coverage for those cases.

Written by the indexing model from the issue text.