Mason Reed

A good idea would be to watch for [new memflow versions](https://crates.io/crates/memflow/versions) and check if it compiles and passes the [tests](https://github.com/memflow/memflow-py/tree/master/tests) (ONLY WITH [LATEST TAG](https://github.com/memflow/memflow-py/releases/latest)). If it passes, then we should...

When a breaking change occurs the minimum version of memflow will get bumped up. [The first workflow](https://github.com/memflow/memflow-py/issues/7#issue-1501747029) should adhere to this minimum version ([specified in the Cargo.toml](https://github.com/memflow/memflow-py/blob/1fc9d3d4133aff4a91bbb159df616ae712c7dd2a/Cargo.toml#L22)).

Should be noted we prefer one over the other right now, we should use the native byte order of the system for the default `Structure`.

> In process.rs there is a comment starting on line 259 stating that Process.address() returns the address of the PEB. Upon testing, I found that it actually is the address...