Thanks for catching that! You're absolutely right, it's a bug in the cost calculation. I'm fixing it right now and I will release an update later today to solve this. Thanks for the heads up :)