Fixes to STAMP Benchmarks

* genome.Genome => one of the worker threads was running in the main thread,
which was replaced by a new thread similar to the others. Furthermore, the
await() condition through the genome.Barrier object was replaced by the join()
to each worker thread.

* genome.Sequencer => the empty version of the atomicMethodFive was replaced by
the atomicMethodFive2 in comments, which includes an implementation. With the
original  empty atomicMethodFive the Genome was crashing.

* kMeans .kMeans => replace the FileImputStream with getResourceAsStream that
allows to read the configuration file from any location in the classpath. In
this case, we are reading the KMeans input file from the deuceTests.jar.

* ssca2.GetUserParameters => change the type of two arguments from double to integer.

* vacation.Client => move the parameterization arrays into their own atomic
operation. This change turns these arrays private to their transactions.
Fixes to StmBench7:

* DeuceSTMOperationExecutor => split the atomic block in two separated blocks,
one for the execution of read-only operations and other for read-write. Some
STMs, such as the LSA, keep track of the functions  that perform write
operations and for those ones it will not try to execute read-only transactions.
So to take advantage of the lightweight behavior of read-only transactions we
need to keep a separated method reserved for the execution of read-only
operations, otherwise the STM will not perform read-only transactions.

* BenchThread => this class keeps two multi-dimensional arrays to register the
operations TTC and highest TTC log. Yet, the captured analysis mechanism has a
limitation regarding multi-dimensional arrays, due to the big overhead of
unwrapping the encapsulated array from a captured state object. So every time an
unwrap operation occurs within the capture analysis , then it raises an
exception alerting the end-user programmer. In this case, one of the recommended
workarounds is to access those arrays through atomic indexers (which are
performed within a transaction) and avoid the unwrap. For this purpose we
included atomic indexers in the BenchThread  class to access the mentioned
multi-dimensional arrays.

* BenchThread => the system property uniqueop can specify a single operation to
be executed by this benchmark.
New build.benchmarks.xml to execute Deuce benchmarks

* build.benchmarks.xml => includes the main configurations for the execution of all benchmarks included in the Deuce distribution. For each benchmark provides both configurations with, and without, the runtime capture analysis activated.

* AvailableMem and AvailableProcs => utility classes used by the build.benchmarks.xml.
Merge pull request #2 from fmcarvalho/fix/benchmarks

Fix/benchmarks