Apparently that didn't remotely work and the bug was just hidden by the fact our example code had nothing to eliminate. Fixed now, though!