You are right, that you may have loads of problems when writing data (and code) to DB because you will loose what is outside DB encoding. That's exactly what is already happening to DaveE, so that will not be a new problem for him. Also if you keep in mind that you have to stick to only those characters that can be handled by DB (for example Cyrillic and basic Latin characters in my case, and Windows-1252 in case of DaveE), the problem does not have such a big impact on you work.
Anyway I should have warned DaveE of those risks and did not, so am grateful that you did. Thank you.

IvanZ / Hilarion,

Thank you both for your responses.

Unfortunately, turning back on Unicode support and launching it with NLS_LANG environment variable set, did not work either.

For the time been, I will be using the workaround IvanZ suggested, using the chr(172) representation.

Hopefully, somebody from Allround Automations will be able to comment on whether this will be addressed for future releases.

Thanks again for your help,
Dave