Some calls to Event::Event ctor require a very particular load sequence from .data section

[robojumper]

The ctor at 800a0c40 is sometimes called with a pattern like this:

ss/src/REL/d/t/d_t_ship_window.cpp

Lines 82 to 88 in 22a5cad

	// this works but I don't like it
	static volatile u32 FLAGS_1 = 0x00000001;
	static u32 FLAGS_2 = 0x00100001;
	u32 f1 = FLAGS_1;
	u32 f2 = FLAGS_2;
	Event e = Event(mOffEventId, roomid, f2 & ~f1, nullptr, nullptr);
	mEvent.scheduleEvent(e, 0);

Every call has its own copy of these statics even within the same file, and the volatile seems to be required to load them in the right order. This looks like an obvious hack but we haven't found a good way to match it...

[elijah-thomas774]

Another thing to note:
0x00100001 is a common parameter to creating an event.
This usually is an immediate load, but in the cases of & ~f1 both become data. f1 is also consistently 0x00000001 in these cases