@Override
	public Entry<TraceAddressSnapRange, TraceMemoryState> getViewMostRecentStateEntry(long snap,
			Address address) {
		return getViewMostRecentStateEntry(snap, new AddressRangeImpl(address, address), s -> true);
	}
TODO: I don't remember why I prohibited this originally. It seems some technicality in
calling something "last known?" We might revisit and specify that definition, in the face
of memory being invalidated while the target is suspended. It seems appropriate to leave
the stale bytes in the trace, but change the state to UNKNOWN. Do those stale bytes still
count as last known? Aside from getBytes, I don't see anything that requires a precise
distinction. We might be careful how this interacts with removeBytes, though.... Well,
AFAICT, it doesn't depend on state markings. For now, I'm going to allow it. We'll see
what happens. Changing this had no effect on the unit tests :/ .
Ghidra/Debug/Framework-TraceModeling/src/main/java/ghidra/trace/database/memory/DBTraceMemorySpace.java