Statistically speaking then what you're saying is I would have to make a baseline of demonstrating probability if given 1 week, 1 month, 1 year. etc... of time to break the code?
since the timer is going to increase per failed attempt I could see how trying to prove the actual amount of time would become pretty complex...
		
		
	 
What he is saying is that statistics can't tell you how long it will take to find the right code. You might get the code right on your first try and then it would have only taken you 2 seconds. What statistics can tell you is, if the code is randomized on each trial, and you do a large number of trials, this is how long it would have taken you on average per trial. Any individual trial has a completely random (within limits) amount of time to compete. 
It is exactly like tossing dice. If you toss one die how many tries will it take you to toss a 5? It could roll a 5 on the first try! But If I tried to roll a hundred fives it would take me very close to 600 rolls to do so, but even after 599 rolls I don’t have any more information about what that next roll is going to be. 
	
		
	
	
		
		
			Zebano, the idea does not have to be useful, i just think it would be interesting and of course I do need to do my project on something......
		
		
	 
This is actually very useful information, and I would be surprised if someone out there has not already posted the information. It tells us quite a lot about the security of the iphone.