Introducing 'nested-change' to avoid pitfall #2 (issue #28)