SynthesizePNTest: Fix for addition of impure regions

Signed-off-by: Uli Schlachter <uli.schlachter@informatik.uni-oldenburg.de>
Fix some checkstyle warnings

Signed-off-by: Uli Schlachter <uli.schlachter@informatik.uni-oldenburg.de>
Fix bug in one of SynthesizePN's constructors

Signed-off-by: Uli Schlachter <uli.schlachter@informatik.uni-oldenburg.de>
Fix Region.getNormalRegionMarking()

If a state is reachable via more than one path from the initial node, the choice
of path shouldn't influence the number of token that is reached. Thus, the
calculation of the initial number of token should be independant of the specific
path that the spanning tree gives to us.

However, the old implementation of getNormalRegionMarking() handled the last
event on the path specially and thus behaved differently depending on the path.
Fix this by just removing this special handling.

Signed-off-by: Uli Schlachter <uli.schlachter@informatik.uni-oldenburg.de>
Remove some dead code

Signed-off-by: Uli Schlachter <uli.schlachter@informatik.uni-oldenburg.de>
Remove accidental debug output

Signed-off-by: Uli Schlachter <uli.schlachter@informatik.uni-oldenburg.de>
Fix the impure region calculation

We want the event to have a backward weight of exactly m. The previous code
increased the backwards weight too much in case it was already non-zero before.

Signed-off-by: Uli Schlachter <uli.schlachter@informatik.uni-oldenburg.de>
Minor improvements

Signed-off-by: Uli Schlachter <uli.schlachter@informatik.uni-oldenburg.de>