Until now the code has by accident added a property with the attribute
MAYBEVOID (which is that one which has the value 1), while the
intention obviously was to use BOUND|REMOVABLE. Whether this has
caused unintended consequences, or been harmless, and whether this fix
now then will cause unintended consequences, no idea.