[TIMOB-16873] iOS: Switch Controls in ListViews are not reused correctly

When using Switches in ListViews that contain a large enough number of records so that the user must scroll (I'm using 40 in this test), the Switch components are not reused correctly. In the attached test, you can see that tapping the switch in the first row will cause it to change in other rows as those rows are later rendered (and the switch components are reused).

Steps to reproduce

Create an app with the following files:

var items = [];
for(var x=0;x<40;x++){
	items.push({
		template: "tpl1",
		lbl: {
			text: "Switch #" + (x+1)
		},
		done: {
			itemId: "sw_"+x,
			value: false
		}
	});
}
$.main.setItems(items);

$.index.open();

function handleChange(e){
	console.log(JSON.stringify(e,null,2));
}

<Alloy>
	<Window class="container">
		<ListView id="list" defaultTemplate="tpl1">
			<Templates>
				<ItemTemplate name="tpl1">
					<View width="Ti.UI.FILL" height="50">
						<Label bindId="lbl" left="5" />
						<Switch bindId="done" right="5" onChange="handleChange"/>
					</View>
				</ItemTemplate>
			</Templates>
			<ListSection id="main" />
		</ListView>
	</Window>
</Alloy>

".container": {
	top: 40,
	backgroundColor:"white"
}

Run the app and click on the first switch in the list

Scroll down and look at the other switches (need to at least scroll past the last record on the first page)

Expected Results

Only the switch that was tapped should change.

Actual Results

Other switch components are changed as well after scrolling.

Additional Info

Sometimes, scrolling back to the top will show that the wrong switch is modified (depending on the size of your list). I've also been able to reproduce this with text fields if they all start out with the same value or and empty string (""). Seems the reuse issue is somehow related to the initial value of the editable component. In this example, all switches start out in the false ( off ) state.