Well, with indirect addressing, you just need to be more careful.
If you want a possible alternative to that here are a couple of methods:
1. Accept the rung, but do not Test it until you have right clicked on the indirect address in question and verified its existence by clicking "Go To Data Table". The file monitor window should pop up with the indirect address highlighted by the cursor. If it does not exist, I believe it will put the cursor on the first element in the file (which it will also do if the element in the brackets happens to contain a "0"). So, in addition to that little check, go ahead and manually look at the address in the brackets [...] and make sure it is there. Then, test the rung.
2. Put a LIM test in series with your indirect address logic so that it will not be scanned unless the address is within the file limits. I use this method in one particular program of mine and it works very well. A LIMit test, is a range check, like a GEQ and LEQ in series, but in one instruction, in case you aren't familiar with it.