We cannot trust Java finalizers to run at appropriate time, if ever

Due to the small size of Java objects, compared to the underlying size
of Z3's trees, java objects are not necessarily collected in due time.
This causes implicit leaks that end up using the entire RAM before Java
moves a finger.

This alternative collects memory in a one-time pass-through, when
deleting a context. Some special usages of ScalaZ3 might thus suffer
from the change.
Make sure we check everything at compile-time, fix warnings
Fix javah by explicitly providing scala-lib in classpath
Re-introduce implicit conversion for ASTVector to Seq
support for real arithmetic
power operator
Remove tests about array default values
Bundle libz3 within scalaz3.jar

The loading of the libz3 is now deterministic, no more LD_LIBRARY_PATH
needed. libscalaz3/libz3 are always expected to be extracted to
<tmp>/SCALAZ3_<checksum>.

Works on linux and mac, compiles on windows but errors when running.
Release ScalaZ3 2.1 with libz3 bundled
Fix equals/hashcode invariant
Let's avoid being lazy, with proper hashcode definition
Remove warnings related to -Wreturn-type
Fix all kinds of warnings
Mods necessary to load dependent libraries under Windows
Mods necessary to load dependent libraries under Windows
Merge branch master into VS2012Express