Basically incidentally what happens is that the code for Compile_Time_Known_Value does a lot of quite complex tests. If something fails in one of these tests, we simply answer False, which is always safe. But it does seem odd that this fails in this csae indeed.