Klever

We know that CPAchecker has quite many assumptions that can result in strange verification results. For instance, it does not track array elements except the first one. Tests should explicitly demonstrate this. Likely here is the most important and often annoying assumptions:

1. Memory tracking (if there isn't memory allocation or it is too complicated then CPAchecker does not track it).
2. Arrays tracking.
3. Function pointer assumptions (nothing is called if function pointer is unknown).
4. Bitwise support (by default it is not performed yet).
5. Ignoring assembly code (sometimes that hits).

Note that specific rules like generic:memory and sync:race have a lot of other assumptions - corresponding tests are also welcome.