Inconsistencies between GRA and MMM

[l-kent]

In some cases, the GlobalRegionAnalysis will assign regions to accesses that do not match up with the regions later found in the MemoryModelMap.

For correct/basic_lock_read/gcc:BAP, there is an inconsistency between the GRA result and the MMM. The GRA correctly gives a region with start address 69652 (0x11014) and size 4 to accesses to that address, but this region does not appear in the MMM's dataMap. I haven't yet identified why.

For correct/secret_write/clang:BAP, there is a new error introduced by the most recent changes. The GRA correctly gives accesses to address 0x11034 (69684, which is the address of z) a region, but this region is not included in the MMM's dataMap.