Previously, new VMA entries were always prepended to the list of the associated MappedResource. This usually made FirstVMA erroneously point to the *highest* VMA instead of the lowest.