I'm not sure I like the amount of const_cast and mutable going on, I'd rather leave it const-incorrect for now and find a different solution somehow. (So far it doesn't look like const correctness is solving an existing problem?)

I'll be honest, I'm not sure what the original intent of this patch queue was. I think the std::vector pointers, maybe?

Making NetworkAddress const correct was necessary for std::find, and I'm pretty sure I've run into it before

3 const_casts + 3 mutables vs only 2 const casts previously, but the object is now "more correct" conceptually, I think?

Not worth it until we have a proper reason to, i think