How to engineering around Imgui owning variables?

Imgui uses a lot of pointers for its internal use and as such, tends to "own" various variables. We could avoid this by simply passing it the pointer to our variable say, but then again I really don't want to deal with pointers math (for aesthetic and technical reasons)

Currently, we deal with this by having to write more code.

Start by locating the C++ code that integrates Imgui and the current variable-handling paths; the issue does not name files, tests, or entry points. Compare how Imgui-owned pointers are currently managed with the desired approach, and clarify the acceptable ownership and pointer-arithmetic constraints before defining what completion means.

Written by the indexing model from the issue text.