- since the cpu/sys information is invariant, it doesn't make much
  sense to emit by default at every time-step.

- use InfoSwitch to disable, or via static method.

- respect the state of the argList banner when deciding to emit
  initialization information. Can otherwise end up with unwanted
  output rubbish on things like foamDictionary and foamListTimes.

- nested classes can't be forward declared and thus less flexible
  than desired

- output as dictionary format instead of PtrList.
  Makes it easier to manipulate (changeDictionaryDict, foamInfoExec).

- provide a static profiling::print(Ostream&) method to output
  values to a log file.

- For example, decomposePar use multiple simultaneous Times.
  So permit multiple initialization without a warning. (issue #157)

BUG: memInfo not activated by -profiling option (fixed #157)

- value corresponds to the max memory when the corresponding profiling
  is started.
  Only used when the top-level profiling has memInfo active.

- memInfo is disabled by default, since the new maxMem functionality
  otherwise adds overhead with every call.

tutorial:
    /lagrangian/reactingParcelFoam/verticalChannelLTS

- this option overrides any controlDict settings as a convenient means
  to selecting profiling without messing with the controlDict.

- provide Profiling::writeNow() to emit profiling for utilities that
  don't have any natural time increment mechanism to trigger it.

- basic cpuInfo (model identification, MHz, etc)
- process memInfo

- profiling is activated via the case system/controlDict by
  adding a "profiling" sub-dictionary.

  Simply add the following (everything enabled):

      profiling
      {}

  Which corresponds to the longer form:

      profiling
      {
          active      true;  // default: true
          cpuInfo     true;  // default: true
          memInfo     true;  // default: true
          sysInfo     true;  // default: true
      }

  This can be used to selectively disable any extra information
  (eg, you don't want anyone else to know what hardware was used).

- not de-referenced and no current issues, but cleaner this way

- activate via the case's <system/controlDict>:

      profiling   yes;