Refers to #36

Refers to #36

Refers to #36

Refers to #36

Refers to #36

Currently it is testing both approaches for checking the CPU load, each
for ten seconds. Messages are printed to the console using NLog.

Refers to #36

Refers to #36

Refers to #36

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

Important if it has already been removed before, otherwise the updater
would stop at this point.

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

Refers to #3

This usually happens when VS is building multiple projects at the same
time, hence running the prepare-script multiple times at once.

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