Big input files consume a lot of memory #2

Exhaustive testing will lead to big input files (obviously, due to combinatorial explosion), which currently makes evunit take a lot of memory (everything is read into memory before processing even begins.

It might be possible to use serde to generate a "streaming" deserializer, for example.