Class: ResourceMonitor

[Dean Roddey]

I updated this one a bit to better define the common scenarios. I'm looking at a new Brultech GEM module driver and it really does lend itself to a multi-unit type naming convention, which I'd originally said wasn't used by this device class. But in a case like the GEM, which offers multiple channels, each of which provides the same measurements. it makes use to use sub-unit naming and let the user/device provided name to be the sub part and the field names for each sub unit to be the (identical, repeated) values provided.

If it's just a free form type of thing, where each value is really a separate thing, not really a set of repeated values, then don't use the sub-unit naming. Sub-unit is only ever valid when all sub-units have identical values.