added some more test cases
no longer propagating explicit taints into methods that have already been analyzed for implicit flows since this has already generated a superset of the possible explicit taints
Merge branch 'develop' of github.com:secure-software-engineering/soot-infoflow into develop

Conflicts:
	test/soot/jimple/infoflow/test/junit/ListTests.java
prevented unnecessary abstraction cloning
narf
1) added another test case
2) re-enabled one testcase that used to take forever, but now works
3) purging postdominators where we don't need them
4) removed dead code
5) added some assertions to detect spurious abstractions
6) fixed a wrong condition for taint activation
1) disabled debug mode for ant builds
2) not passing on zero values if a seed was not a source
3) now detecting sink calls with constant parameters if the underlying class was instantiated conditionally
fixed string concatenation test case
Got rid of a false positive that occurred when a field in the target object was tainted, but not the whole target object as such. In this case, a sink invoked with a constant string in the target object's code should not be considered a leak in implicit flow mode.
performance optimization
added yet another implicit flow test case
version succeeding on all test cases
fixed npe
extended timeout for test case
added support for source/sink managers that treat fields as sources
removed Java warning
added a handler for notifying external clients about propagated taints
added missing interface
(1) fixed a test case that failed to reset the access path lengtrh
(2) duplicated a test case with a shorter access path length and fixed the code to correctly handle this case
(3) added a test case with two secret integers being added and the result being leaked and fixed the path construction algorithm for the test case to work
cleaned up the code and added an assertion