But I employ various strategies to minimise the pairing. Even if it means agreeing with another co worker to say that we paired on a task. Essentially lying.

Don't do that.

If you genuinely feel that pair programming is making you less productive, take it up with your manager. Suggest some metrics by which to measure your productivity and ask for a 1 month trial period of working alone vs. working in a pair. If they agree; great, here's your chance to prove your assertion.

But if they come back and say "no, we feel that pair programming is part of our team culture", then you have two choices: adapt or leave.

If you really disagree with any given practice in work environment, you should absolutely say so. In fact you have a moral responsibility to your employer to do so. But if after you've discussed it with the team and people have made their decision, then you should abide by that. There's nothing worse than someone on the team poisoning the environment. If you really feel that strongly about it, then the only moral course of action is to find another job.

Personally, I think pair programming can be useful in certain circumstances (training a novice, working on a task that's open-ended, etc.) but yeah, for the majority of the time, it's a massive resource drag.