I worked with Amir on this issue. The problem is caused by a bug, and the fix is already implemented (ALE2918), which will be included in future releases. Right now, the plan is to include the fix in 2017.2+.