On an integer overflow while being in low-load state the probation
counter should not be reset to zero (indicating the load limit was
violated) but rather to the lowest value representing a valid load
(being _probation + 1).

Refers to #36

Refers to #36

Refers to #36

Refers to #36

Refers to #36

Refers to #36

Placed in namespace ATxCommon.Monitoring, using its own timer to update
the values.

Refers to #36

This way an email will be sent to an admin if configured so they have a
chance to check what's going on.

Megabytes have shown to be a bit clumsy in the configuration files, so
simply switch to the more useful Gigabytes unit.

Fixes #39

Refers to #36

Refers to #25

Refers to #24

Allow setting the log level explicitly from "Warn", "Info", "Debug" or
"Trace" in the configuration.

Default is "Info", fallback for invalid settings is "Debug".

Fixes #34

They were accidentially removed in commit cf183560 believing they had been
correctly moved by Visual Studio when refactoring the code and just forgotten
in the directory hierarchy. Who could guess Windows is so ignorant when
resolving paths?

Note that they are not included in the example configuration files as
these settings can easily mess up everything and should only be adjusted
with great care.

The default settings are valid on Windows 7 and Server 2012 and were
successfully tested on those versions.

Fixes #11

If a new directory is found in incoming but the move operation to
processing failed for some reason, the timestamp and username
directories (and potentially some partially moved data?) would remain
in processing. To prevent confusion about those "incomplete" transfer
candidates they are moved to the "ERROR" location.

The shared approach results in conflicts if the generated class is used
in ATxCommon which is imported in the other projects. This way we can
use the symbols defined via ATxCommon in all depending projects.

The downside is that it slows down the build-process a bit as every
build from a project depending on ATxCommon (read: all others) will
change the generated code and thus force a re-build of ATxCommon and
the project itself. Since building the entire solution is still just
a matter of seconds, that's a fair trade-off.

Refers to #18

Refers to #18, #29

Refers to #18, #28, #29

Refers to #29

Refers to #28

Refers to #28

Refers to #28

Those objects are not meant to be instantiated directly but only using
the Deserialize() methods which takes care of creating a new object in
case deserializing fails for the status class.

This way the value is directly visible in the code where the property is
created, improving readability. Setting defaults in the constructor is
therefore not necessary any more.

Refers to #29