We must compare to 'sat'...

Arguments and Instructions had a separate id, so when we put
them to the same dictionary, everything got messed.

The world will be much nicer when we can run the analysis
on real code. Mainly for testing 8-)

And give more statistics.

Introduce the boolean type to avoid confusion between bitvector of size
1 and boolean (solvers distinguish that). So now we have three possible
types:

- value (with a given bitwidth)
- pointer to value (to value with unspecified bitwidth, just pointer. Pointer
itself has a bitwidth)
- boolean (there's no pointer to boolean, boolean is used just as a
result of computations, can be stored/loaded, but no arith operations
on it are allowed yet)

Do it early in the project.

And delegate the operations from exprmanager to it.

Code taken from Symbiotic

Return a list of new/transformed states from execute().

So that we can specify how much bytes from/to memory we write.

With more pointers