What's devs standpoint on writing to inactive segments?

As I understand from documentation, I'm supposed to activate up to 10 segments so I can read from them and they'll automatically be saved at the end of the tick. However the way it is implemented makes it possible to:

1. Write to a segment without activating it in previous tick. Up to 10 segments can be saved.
2. Activate 10 segments, read whatever is stored in them, then for (let key in RawMemory.segments) delete RawMemory.segments[key]; and then write to up to 10 different segments.

I see it as an unharmful undocumented behaviour, similar to memhack, but it also could be considered an exploit.

Can be easily reproduced by trying to zoom into W10N10 on default private server map.

@systemparadox I don't see how public segments or terminal.send descriptions don't fulfill that role.

A structure that can be built in owned room, generates score but compromises room defenses, so disabling towers, disabling walls/ramparts in some way.

By calling Creep.withdraw with nonempty string as an amount argument you can empty storage from resource being withdrawn and make it dissappear. Tested in sim.

Edit:
Steps to reproduce

1. Have a storage with energy in it
2. Have a creep with carry part next to the storage
3. Call creep.withdraw(creep.room.storage, RESOURCE_ENERGY, 'qwerty');

Energy should no longer be inside of storage, nor inside of creep carry parts.