(possible) bug: unset bool val on krm obj

[acpana]

Out of my work around the KRM filler and fuzzer I've observed that a bool set to false on the API object is not set on the KRM obj. Even if that value was expressed in the spec previously expressed as user intent. For instance:

	boolV := false // valid previously user set value that is not in the API obj
	krmBoolv := direct.LazyPtr(boolV) // nil not a pointer to false

could cause extra API calls if we wrongly detect a diff.

Note: I'm still investigating this and I want to see this happen end to end (in a test)